Communication service for machine-to-machine devices

ABSTRACT

When machine-to-machine (M2M) devices attach to a mobile communication network, the associated communication session can be treated differently than the attachment of other devices. For example, upon determining that a subscriber device that attaches to a communication network is an M2M device and has completed a given network transaction, the M2M device can be immediately detached without waiting on expiration of an inactivity timer. As another example, upon determining that a subscriber device that attaches to a communication network is an M2M device, the M2M device can be excluded from various signaling procedures such as load-balancing procedures.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of, and claims priority to,U.S. patent application Ser. No. 14/699,725, filed on Apr. 29, 2015 andentitled, “COMMUNICATION SERVICE FOR MACHINE-TO-MACHINE DEVICE”. Theentirety of this application is hereby incorporated herein by reference.

TECHNICAL FIELD

The present application relates generally to providing communicationservice for a subscriber device according to different protocols inresponse to a determination that the subscriber device is amachine-to-machine (M2M) device.

BACKGROUND

The number of subscriber devices that connect to wireless networks hasbeen growing at a very fast pace for many years. In the past, consumerpurchase of manually-operated devices such as smart phones, tablets,etc. has driven the majority of the growth. However, a recent trend hasstarted to emerge in which a different class of device is beginning todrive a significant proportion of the growth of subscriber devices thatutilize wireless network services. Machine-to-machine devices such assmart meters, smart appliances, or the like, are not manually operatedby a user when connecting to the network and communicating data but areincreasingly becoming subscribers of wireless networks. It is expectedthat by the year 2020, M2M devices that use wireless network serviceswill grow to the billions, possibly many hundreds of billions.

BRIEF DESCRIPTION OF THE DRAWINGS

Numerous aspects, embodiments, objects and advantages of the presentinvention will be apparent upon consideration of the following detaileddescription, taken in conjunction with the accompanying drawings, inwhich like reference characters refer to like parts throughout, and inwhich:

FIG. 1 illustrates a block diagram of an example system that can providefor enhanced machine-to-machine (M2M) communication service inaccordance with certain embodiments of this disclosure;

FIG. 2A illustrates a block diagram illustration of several suitableexamples of the M2M device in accordance with certain embodiments ofthis disclosure;

FIG. 2B illustrates a block diagram illustration of various examples ofthe access point device in accordance with certain embodiments of thisdisclosure;

FIG. 3 illustrates a block diagram illustration of several examples ofdata that can be used to make the M2M determination in accordance withcertain embodiments of this disclosure;

FIG. 4 illustrate a block diagram of an example system that depictsexamples related to forwarding detach messages and to excluding M2Mdevices from certain signaling procedures in accordance with certainembodiments of this disclosure;

FIG. 5 illustrates a block diagram of an example system that provides asubscriber-side implementation in connection with enhanced M2Mcommunication in accordance with certain embodiments of this disclosure;

FIG. 6 illustrates a block diagram of an example system that depictsadditional aspects or elements in connection with the subscriber-sideimplementation in accordance with certain embodiments of thisdisclosure;

FIG. 7 illustrates an example methodology that can provide for enhancedmachine-to-machine communication service in accordance with certainembodiments of this disclosure;

FIG. 8 illustrates an example methodology that can provide foradditional elements or aspects in connection with enhancedmachine-to-machine communication service in accordance with certainembodiments of this disclosure;

FIG. 9 illustrates a first example of a wireless communicationsenvironment with associated components that can be operable to executecertain embodiments of this disclosure;

FIG. 10 illustrates a second example of a wireless communicationsenvironment with associated components that can be operable to executecertain embodiments of this disclosure; and

FIG. 11 illustrates an example block diagram of a computer operable toexecute certain embodiments of this disclosure.

DETAILED DESCRIPTION Overview

Conventional mobile communication networks attempt to provide servicesto all subscriber devices that are provisioned to access a given service(e.g., a communication service). Such services are generally provided toa subscriber device in response to a request from the subscriber deviceto attach to the network. Managing services can be expensive in terms ofresource utilization. For example, once the subscriber device isattached to the network, network devices of the communication networktypically must manage the various states of each attached subscriberdevice, such as, e.g., UE idle or active state managed by eNB, mobilityanchor state for all sessions managed by S-GW, IP anchor state for allsessions managed by P-GW, and mobility state, tracking area, andhandover state of UE managed by MME, etc. Managing state information canbe resource-intensive for many different network nodes, includingserving gateways, packet data network gateways, and mobility managemententities, all of which typically reside in the core network (CN) portionof the communication network. In addition, state information issometimes also managed by access point devices or other devices thatreside in the radio access network (RAN) portion of the communicationnetwork as stated in the examples above.

Unfortunately, conventional mobile communication networks are notespecially scalable in terms of managing state information associatedwith attached subscriber devices. In this regard, the expected growth ofmachine-to-machine (M2M) devices in the near future will placeadditional stress on network components that those network componentsmay not be able to handle in a cost-effective manner.

The disclosed subject matter relates to treating M2M devices (e.g.,meter readers) as a special case when attaching and providing services,and to delivering services to M2M devices based on need, which isgenerally much lower than the needs of mobile phones or other manuallyoperated user equipment. In some embodiments, an access point (AP)device (e.g., eNodeB, femtocell, etc.) can receive a request from asubscriber device to attach to the network. The AP device can determinethat the subscriber device is an M2M device in one of several ways. Uponmaking this determination, the AP device can treat the communicationsession for the M2M device differently than communication sessionsassociated with other subscriber devices. For example, the AP device canreceive communication data from the M2M device (e.g., typically ascheduled transmission and often a fixed amount of data) and/or send(e.g., often also scheduled) communication data to the M2M device.Thereafter, the AP device can immediately detach the M2M device withoutthe need to wait for the expiration of an inactivity timer, therebyfreeing up valuable resources that can be allocated to other devices.

It is understood that conventional communication networks employinactivity timers to signal when to detach idle devices, which is veryuseful for mobile devices where inactivity is common In those cases,allowing the attached device to stay attached, even when idle, can bemore efficient than detaching the device as soon as it becomes idle,since signaling associated with establishing a connection (e.g.,attaching) is relatively resource intensive. Hence, conventionalcommunication networks allow a subscriber device to remain attached inan idle state as a trade-off to avoid repeatedly detaching andre-attaching the subscriber device that is in use by the operator, buthappens to be idle for short periods of time.

While use of these inactivity times can be extremely useful for manysubscriber devices, M2M devices generally do not come with the sameuncertainty as to whether an idle period means the user is justtemporarily idle or use of the network service is complete. In thisregard, the disclosed subject matter can efficiently handle largenumbers of M2M devices in an efficient manner Such can on average reducesignaling overhead as well as resource allocation for all devicesattached to the network, particularly when a significant portion of theprovisioned devices are M2M devices.

The disclosed subject matter can further reduce power requirements forM2M subscriber devices, which can be very advantageous not only forusers associated with M2M devices, but also in terms of meeting thestringent battery life requirements defined by communication standards.For example, third generation partnership project (3GPP) standardsrequire that M2M devices be equipped with batteries that willsufficiently power those devices for many years without replacement. In5G, the M2M device required battery life is extended to 10 years orlonger. By immediately detaching the M2M device after communication datais sent (without waiting on expiration of an inactivity time), power canbe conserved at the M2M device. In addition, the AP device canfurthermore conserve M2M power by excluding M2M devices from loadbalancing procedures or other procedures, as further detailed below.

Example Devices to Enhance M2M Communication Service

The disclosed subject matter is now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the disclosed subject matter. It may beevident, however, that the disclosed subject matter may be practicedwithout these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order tofacilitate describing the disclosed subject matter.

Referring now to the drawing, with reference initially to FIG. 1, system100 is depicted. System 100 can provide for enhanced machine-to-machine(M2M) communication service. The enhanced communication service providedto M2M devices can, e.g., reduce the amount of resources required toprovide service to an M2M device and reduce the energy consumption byM2M devices when leveraging a communication network and/or the providedservice(s). Generally, system 100 can comprise a processor and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations. Examples of the memoryand processor can be found with reference to FIG. 11. It is to beappreciated that the computer 1102 can represent a server device of acommunications network or a user equipment device and can be used inconnection with implementing one or more of the systems or componentsshown and described in connection with FIG. 1 and other figuresdisclosed herein.

System 100 can include an access point (AP) device 102 that subscriberdevices 104 utilize to access a communication network and/or servicesprovided by the communication network. Examples of suitable AP devices102 are provided in connection with FIG. 2B. Subscriber devices 104 canbe substantially any device that can attach to a mobile communicationnetwork, via AP device 102. It is understood that the subject matterdisclosed herein relates specifically to M2M devices, which aretherefore a relevant subset of all subscriber devices. Other devicesthat can be considered subscriber devices 104, but are not M2M devices106 are distinguished at reference numeral 108. These non-M2M devices108 can also attach to AP device 102, and in a sense are competing forscarce resources with M2M devices 106, but can be considered for thesake of this disclosure to operate in a conventional manner when doingso. Examples of M2M devices 106 are depicted with reference to FIG. 2A.

AP device 102 can be configured to receive a request 110 to attach tothe communication network via AP device 102. Request 110 can be receivedfrom M2M device 106, which, as discussed above, can be a subset ofpotential subscriber devices 104. In response to request 110, AP device102 can attach M2M device 106 by providing communication network servicefor M2M device 106. Attaching and providing service to M2M device 106 isillustrated by reference numeral 114. At some point before, during, orshortly after attaching and providing service 114, AP device 102 candetermine that the subscriber device 104 making request 110 is an M2Mdevice 106, a special subset of all subscriber devices 104. Thedetermination that request 110 is made by M2M device 106 is depicted asM2M determination 112. M2M determination 112 can be determined innumerous ways, various examples of which are further described withreference to FIG. 3.

Once M2M device 106 is attached, communication data 116 can be receivedfrom the M2M device 106, or in some embodiments transmitted to M2Mdevice 106. After the last byte of communication data 116 has beendelivered, an inactivity timer 120 can be started, since the device hascommunicated the data as intended and can be marked as idle. Inconventional systems, this idle state may be updated by various networkelements, but M2M device 106 will remain attached and therefore continueto tie up allocated resources. This situation remains until aninactivity timer 120 expires (which also requires allocated resources tooperate), at which point, M2M device 106 can be detached.

According to the disclosed subject matter, however, upon receivingcommunication data 116, AP device 102 can immediately detach (element118) M2M device 106 by terminating communication network service for M2Mdevice. Detach 118 procedure can be effectuated independently ofinactivity timer 120 that triggers detachment after expiration of aninactivity timer in conventional systems. It is understood that in caseswhere request 110 is made by non-M2M device 108 (and/or subscriberdevice 104 is not determined to be an M2M device), then detaching canoccur as normal after expiration of inactivity timer 120. But in thespecial case of subscriber device 104 being determined to be an M2Mdevice 106, then detach 118 procedure can implemented immediatelywithout regard to inactivity timer 120. In some embodiments, inactivitytimer 120 need not be used at all (thereby reducing resourceutilization) in response to M2M determination 112. In some embodiments,certain states (e.g., an idle state identifier) need not be updated inresponse to M2M determination 112.

While still referring to FIG. 1, but turning now as well to FIGS. 2A and2B, illustrations 200 and 210 are depicted. Illustration 200 providesfor several suitable examples of the M2M device 106. M2M devices 106generally have certain characteristics that distinguish from othersubscriber devices 104 such as non-M2M devices 108. For example, M2Mdevices 106 generally transmit request 110 and/or communication data 116without manual instruction or an expectation of manual direction,potentially for the life of the device. Unlike most non-M2M devices 108that must contend with mobility, M2M devices 106, at least thoserelevant to the disclosed subject matter, are generally stationary. Insome embodiments, M2M devices 106 generally only transmit request 110and/or communication data 116 according to a defined schedule, which arereferred to herein as scheduled stationary machine-to-machine (SS-M2M)devices.

An example of a suitable M2M device 106 is meter device 202. Forexample, a smart meter that monitors or measures resource consumption ata designated site or premises. Meter device 202 serves as an example ofan SS-M2M device, since meter device 202 is both stationary and may onlyneed to use the communication network according to a defined schedule(e.g., once per month to send consumption data). Another example of asuitable M2M device 106 is appliance device 204. Appliance device 104can be, e.g., a smart refrigerator that, via sensors, determines whencertain goods are in short supply and utilizes the communication networkto transmit appropriate messages. These messages can be scheduled (e.g.,provided to a grocery delivery service or the owner's cell phone as ashopping list once per week) or event-driven (e.g., provided in responseto the short supply). Still another example of a suitable M2M device 106is sensor device 206. In some embodiments, sensor device 206 can senseor measure a physical attribute or quantity. As with appliance device204, sensor device 206 use of the communication network can be eitherscheduled or event-driven, but devices 204 and 206 will generally bestationary.

In some embodiments, various tiers of service can be provisioned to M2Mdevices 106 based on the type of M2M device 106 in question ordesignated service requirements. For example, an SS-M2M device such asmeter device 202 that does not have mobility requirements (e.g., isstationary) and only attaches to the network about once per month tosend meter data (e.g., operates on a defined schedule and has arelatively small data usage) might be provisioned at a very low tierthat is less expensive and less resource-intensive on the network thanhigher tiers. Another provision tier can apply to, for example,appliance device 204 that sends only scheduled messages that certaingoods are in short supply. This type of M2M device is scheduled and thedata usage is small, but the frequency of use is likely higher than formeter device 202 (e.g., scheduled data transmitted once per week vs.once per month), so such might invoke a higher provisioning tier. Asanother example, a third provisioning tier can be provided when M2Mdevice 106 is not scheduled, but rather event-driven. Appliance device204 provides an example here as well, but rather than sending noticesonce per week as in the previous example, the notices can be provided asneeded and driven by the event of short supply, for example. This typeof M2M device is not scheduled, which may increase the network demands,but data usage can be intermittent and the device is stationary, whichcan reduce network demands. As still another example, consider sensordevice 206 that gathers a large amount of data and seeks to transmitthat data daily as well as based on events. This type of M2M device isnot necessarily scheduled, the schedules are relatively frequent, andthe data usage is high. Thus, this M2M device might be provisioned at ahigher tier than the other examples. As can be seen by these examples,provisioning an M2M device based on usage/need can be affected by avariety of factors, many of which are influenced by the demands suchusage places on the communication network. Examples factors can be,e.g., whether usage is scheduled or event-based, frequency of use, datausage and so forth. It is appreciated, however, that most M2M deviceusage will generally be far less resource-intensive on the communicationnetwork than the average non-M2M device 108, so provisioning tiers forM2M device 106 can be especially advantageous for those customers.

Referring specifically to FIG. 2B, illustration 210 can provide forvarious examples of the access point device 102. For example, AP device102 can be eNodeB 212, femtocell 214, or microcell 216. It is understoodthat examples provided herein are for the sake of illustration and notintended to be exhaustive or limiting.

Referring now to FIG. 3, illustration 300 is depicted. Illustration 300provides for several examples of data that can be used to make the M2Mdetermination 112. For example, determining the subscriber device 104 isa machine-to-machine device 106 can be based on any of the following.Service level data 302, Internet protocol (IP) address 304, media accesscontrol (MAC) address 306, user equipment (UE) category 308, indication310 from M2M device 106, and so forth. Service level data 302 can relateto provisioned service level data representative of a level of serviceprovisioned for the subscriber device 104 by an entity of thecommunication network. IP address 304 can relate to an IP addressassociated with the subscriber device 104. MAC address 306 can relate toa media access control address associated with the subscriber device104. UE category 308 can relate to user equipment category datarepresentative of a device category as defined by a third generationpartnership project specification or by another entity. Indication 310can relate to machine-to-machine identification data received from thesubscriber device 104 that indicates the subscriber device 104 is amachine-to-machine device 106.

Turning now to FIG. 4, system 400 is provided. System 400 depictsexamples related to forwarding detach messages and to excluding M2Mdevices from certain signaling procedures. System 400 assumes M2M device106 has already attached to the communication network via AP device 102and has completed transmission of communication data 116, upon which APdevice 102 will typically immediately detach M2M device 106independently of inactivity timer 120. In some embodiments, AP device102 can purge 402 state data 404 associated with a mobility state of M2Mdevice 106 that is managed by or accessibly to AP device 102. Purging ofstate data 404 can be in response to detach 118 procedure and can beindependent of inactivity timer 120.

In some embodiments, AP device 102 can transmit UE detachment message406 to M2M device 106. UE detachment message 406 can relate to anindication that M2M device 106 has been detached. Not all embodimentsrely on the use of UE detachment message 406 as in some embodiments, M2Mdevice 106 has knowledge that M2M devices are being treated differentlyand is aware in advance to detach/power down after communication data116 is transmitted. For other embodiments, however, UE detachmentmessage 406 can serve to conserve power for M2M device 106 instead ofremaining in a power-using, though idle, state.

In some embodiments, AP device 102 can transmit a CN detachment message408 to a core network device 410. Core network device 410 can be, forexample, a serving gateway device, a packet data network (PDN) gatewaydevice, a mobility management entity (MME) device or any suitable devicethat manages or maintains resource directed to the attachment of M2Mdevice 106 such as state data 414 or inactivity timer 416. CN detachmentmessage can include information indicative of the detach 118 procedureand/or indicative of purging 412 of the device state information 414associated with the attaching of the machine-to-machine device 106 andindependently of the inactivity timer 416. In this regard, resources canbe saved due to the immediate detachment of M2M device 106 in both thecore network as well as the radio access network of the communicationnetwork.

Furthermore, additional power-saving mechanisms can be provided. Forinstance, in some embodiments, AP device 102 can provide for exclusion418. Exclusion 418 can relate to excluding M2M device 106 from varioussignaling procedures such as load-balancing procedures. Sinceload-balancing procedures generally require a significant amount ofmeasurements and reporting, excluding M2M devices 106 from theseprocesses can result in a significant power-consumption savings.Moreover, given that M2M devices 106 typically will not benefit fromcertain load-balancing operations, as their spectrum requirements areusually quite minimal, excluding M2M devices 106 from such procedureswill not generally negatively impact the advantageous associated withthose procedures.

Referring now to FIG. 5, system 500 is depicted. System 500 provides asubscriber-side implementation in connection with enhanced M2Mcommunication. While examples provided with respect to FIGS. 1-4 (e.g.,network-side implementations) may in some regards be more efficient inoperation, such also may require certain changes to be made to networkelements. Embodiments illustrated in FIGS. 5 and 6 can be implementedwith fewer or no changes to existing infrastructure. For example, ratherthan (or in addition to) AP device 102 determining that a subscriberdevice 104 is a M2M device 106, the M2M device in question can indicateas much and facilitate detachment at the appropriate time.

System 500 can include M2M device 502 and AP device 504, which canfunction in much the same way as previously described in connection withFIG. 1. For example, M2M device 502 can transmit a request 506 to APdevice 504. Request 502 can be a request to attach to the communicationnetwork via, AP device 504. In response, AP device 504 can attach M2Mdevice 502 and provide the request service and M2M device 502 can beinformed by acknowledgement 510. M2M device 502 can further transmit toAP device 504 M2M identifier 508 that indicated the request to attach isfor a machine-to-machine device. M2M identifier 508 can be transmittedwith request 506 or as part of a separate message. M2M identifier 508can be based on examples provided herein in connection with FIG. 3 andis intended to inform AP device 504 of the status of device 502 as anM2M device and thus that upon completion of transmission ofcommunication data 512, the communication session can be terminatedimmediately without waiting on expiration of an inactivity timer.

Hence, in response receiving acknowledgement 510 that the M2M device 502is attached to the communication network via AP device 504, M2M device502 can transmit communication data 512 to AP device 504. Uponcompletion of the transmitting of the communication data 512, M2M device502 can detach 514 from the communication network by terminating acommunication network service provided by AP device 504 independently ofan inactivity timer that triggers detaching after expiration of aninactivity period.

Turning now to FIG. 6, system 600 is provided. System 600 illustratesadditional aspects or elements in connection with a device-sideimplementation. In some embodiments, M2M device 502 can transmit to theAP device 504 an AP purge message 602. AP purge message 602 can instructAP device 504 to purge 606 state information 608 associated with theattaching of M2M device 502 and to do so independently of the inactivitytimer.

In some embodiments, M2M device 502 can transmit to the AP device 504 CNpurge message 610. CN purge message 610 can instruct a device of thecore network (e.g., an SGW device, PGW device, MME device, etc.) topurge state information associated with the attaching of M2M device 502and to do so independently of the inactivity timer. CN purge message 610can be forwarded to the appropriate core network device(s) by AP device504.

In some embodiments, M2M device 502 can transmit to the AP device 504non-participation message 612. Non-participation message 612 caninstruct AP device 504 that M2M device 502 is to be excluded fromparticipation in signaling operations such as load-balancing signalingoperations.

Example Methods to Enhance M2M Communication Service

FIGS. 7 and 8 illustrate various methodologies in accordance with thedisclosed subject matter. While, for purposes of simplicity ofexplanation, the methodologies are shown and described as a series ofacts, it is to be understood and appreciated that the disclosed subjectmatter is not limited by the order of acts, as some acts may occur indifferent orders and/or concurrently with other acts from that shown anddescribed herein. For example, those skilled in the art will understandand appreciate that a methodology could alternatively be represented asa series of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with the disclosed subject matter.Additionally, it should be further appreciated that the methodologiesdisclosed hereinafter and throughout this specification are capable ofbeing stored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers.

Turning now to FIG. 7, exemplary method 700 is depicted. Method 700 canprovide for enhanced machine-to-machine communication service. Forexample, at reference numeral 702, an access point device comprising aprocessor can receive a request from a subscriber device to attach tothe access point device of a communication network.

At reference numeral 704, the access point device can determine thesubscriber device is a machine-to-machine device that transmits therequest (e.g., the request received at reference numeral 702) andassociated communication data (e.g., communication data received atreference numeral 708) without manual instruction.

At reference numeral 706, the access point device can attach themachine-to-machine device to the communication network by providing acommunication service for the machine-to-machine device. At referencenumeral 708, the access point device can receive the communication datafrom the machine-to-machine device.

At reference numeral 710, in response to the receiving the communicationdata (e.g., at reference numeral 708), the access point device candetach the machine-to-machine device by terminating the communicationservice for the machine-to-machine device independently of an inactivitytimer that triggers detaching after expiration of an inactivity period.Method 700 can proceed to insert A, which is further detailed inconnection with FIG. 8, or end.

With reference now to FIG. 8, exemplary method 800 is illustrated.Method 800 can provide for additional elements or aspects in connectionwith enhanced machine-to-machine communication service. For example, atreference numeral 802, the access point device can exclude themachine-to-machine device from participation in a load balancingsignaling procedure or another signaling procedure. Such an exclusioncan be in response to the determining the subscriber device is a M2Mdevice, for instance at reference numeral 704 of FIG. 7. Excluding theM2M device from such procedures can reduce energy-consumption andfacilitate increased battery life.

At reference numeral 804, the AP device can transmit a detachmentmessage indicative of the detaching detailed at reference numeral 710 ofFIG. 7. The detachment message can be provided to a device among corenetwork devices of the communication network. The detachment message caninstruct the device to purge device state information associated withthe attaching of the M2M device and to do so independently of aninactivity timer. At reference numeral 806, the AP device can transmit adetachment message indicative of the detaching. In this case, thedetachment message can be provided to the M2M device rather than to thecore network device as detailed at reference numeral 806. It isunderstood that the detachment message detailed at reference numeral 804can facilitate more efficient use of core network resources, whereas thedetachment message detailed at reference numeral 806 can facilitatereduced power consumption by the M2M device.

Example Operating Environments

To provide further context for various aspects of the subjectspecification, FIG. 9 illustrates an example wireless communicationenvironment 900, with associated components that can enable operation ofa femtocell enterprise network in accordance with aspects describedherein. Wireless communication environment 900 comprises two wirelessnetwork platforms: (i) A macro network platform 910 that serves, orfacilitates communication) with user equipment 975 via a macro radioaccess network (RAN) 970. It should be appreciated that in cellularwireless technologies (e.g., 4G, 3GPP UMTS, HSPA, 3GPP LTE, 3GPP UMB,5G), macro network platform 910 is embodied in a Core Network. (ii) Afemto network platform 980, which can provide communication with UE 975through a femto RAN 990, linked to the femto network platform 980through a routing platform 910 via backhaul pipe(s) 985. It should beappreciated that femto network platform 980 typically offloads UE 975from macro network, once UE 975 attaches (e.g., through macro-to-femtohandover, or via a scan of channel resources in idle mode) to femto RAN.

It is noted that RAN comprises base station(s), or access point(s), andits associated electronic circuitry and deployment site(s), in additionto a wireless radio link operated in accordance with the basestation(s). Accordingly, macro RAN 970 can comprise various coveragecells, while femto RAN 990 can comprise multiple femto access points ormultiple metro cell access points. As mentioned above, it is to beappreciated that deployment density in femto RAN 990 can besubstantially higher than in macro RAN 970.

Generally, both macro and femto network platforms 910 and 980 comprisecomponents, e.g., nodes, gateways, interfaces, servers, or platforms,that facilitate both packet-switched (PS) (e.g., internet protocol (IP),Ethernet, frame relay, asynchronous transfer mode (ATM)) andcircuit-switched (CS) traffic (e.g., voice and data) and controlgeneration for networked wireless communication. In an aspect of thesubject innovation, macro network platform 910 comprises CS gatewaynode(s) 912 which can interface CS traffic received from legacy networkslike telephony network(s) 940 (e.g., public switched telephone network(PSTN), or public land mobile network (PLMN)) or a SS7 network 960.Circuit switched gateway 912 can authorize and authenticate traffic(e.g., voice) arising from such networks. Additionally, CS gateway 912can access mobility, or roaming, data generated through SS7 network 960;for instance, mobility data stored in a VLR, which can reside in memory930. Moreover, CS gateway node(s) 912 interfaces CS-based traffic andsignaling and gateway node(s) 918. As an example, in a 3GPP UMTSnetwork, gateway node(s) 918 can be embodied in gateway GPRS supportnode(s) (GGSN).

In addition to receiving and processing CS-switched traffic andsignaling, gateway node(s) 918 can authorize and authenticate PS-baseddata sessions with served (e.g., through macro RAN) wireless devices.Data sessions can comprise traffic exchange with networks external tothe macro network platform 910, like wide area network(s) (WANs) 950; itshould be appreciated that local area network(s) (LANs) can also beinterfaced with macro network platform 910 through gateway node(s) 918.Gateway node(s) 918 generates packet data contexts when a data sessionis established. To that end, in an aspect, gateway node(s) 918 cancomprise a tunnel interface (e.g., tunnel termination gateway (TTG) in3GPP UMTS network(s); not shown) which can facilitate packetizedcommunication with disparate wireless network(s), such as Wi-Finetworks. It should be further appreciated that the packetizedcommunication can comprise multiple flows that can be generated throughserver(s) 914. It is to be noted that in 3GPP UMTS network(s), gatewaynode(s) 918 (e.g., GGSN) and tunnel interface (e.g., TTG) comprise apacket data gateway (PDG).

Macro network platform 910 also comprises serving node(s) 916 thatconvey the various packetized flows of information or data streams,received through gateway node(s) 918. As an example, in a 3GPP UMTSnetwork, serving node(s) can be embodied in serving GPRS support node(s)(SGSN).

As indicated above, server(s) 914 in macro network platform 910 canexecute numerous applications (e.g., location services, online gaming,wireless banking, wireless device management . . . ) that generatemultiple disparate packetized data streams or flows, and manage (e.g.,schedule, queue, format . . . ) such flows. Such application(s), forexample can comprise add-on features to standard services provided bymacro network platform 910. Data streams can be conveyed to gatewaynode(s) 918 for authorization/authentication and initiation of a datasession, and to serving node(s) 916 for communication thereafter.Server(s) 914 can also effect security (e.g., implement one or morefirewalls) of macro network platform 910 to ensure network's operationand data integrity in addition to authorization and authenticationprocedures that CS gateway node(s) 912 and gateway node(s) 918 canenact. Moreover, server(s) 914 can provision services from externalnetwork(s), e.g., WAN 950, or Global Positioning System (GPS) network(s)(not shown). It is to be noted that server(s) 914 can comprise one ormore processor configured to confer at least in part the functionalityof macro network platform 910. To that end, the one or more processorcan execute code instructions stored in memory 930, for example.

In example wireless environment 900, memory 930 stores informationrelated to operation of macro network platform 910. Information cancomprise business data associated with subscribers; market plans andstrategies, e.g., promotional campaigns, business partnerships;operational data for mobile devices served through macro networkplatform; service and privacy policies; end-user service logs for lawenforcement; and so forth. Memory 930 can also store information from atleast one of telephony network(s) 940, WAN(s) 950, or SS7 network 960,enterprise NW(s) 965, or service NW(s) 967.

Femto gateway node(s) 984 have substantially the same functionality asPS gateway node(s) 918. Additionally, femto gateway node(s) 984 can alsocomprise substantially all functionality of serving node(s) 916. In anaspect, femto gateway node(s) 984 facilitates handover resolution, e.g.,assessment and execution. Further, control node(s) 920 can receivehandover requests and relay them to a handover component (not shown) viagateway node(s) 984. According to an aspect, control node(s) 920 cansupport RNC capabilities.

Server(s) 982 have substantially the same functionality as described inconnection with server(s) 914. In an aspect, server(s) 982 can executemultiple application(s) that provide service (e.g., voice and data) towireless devices served through femto RAN 990. Server(s) 982 can alsoprovide security features to femto network platform. In addition,server(s) 982 can manage (e.g., schedule, queue, format . . . )substantially all packetized flows (e.g., IP-based) it generates inaddition to data received from macro network platform 910. It is to benoted that server(s) 982 can comprise one or more processor configuredto confer at least in part the functionality of macro network platform910. To that end, the one or more processor can execute codeinstructions stored in memory 986, for example.

Memory 986 can comprise information relevant to operation of the variouscomponents of femto network platform 980. For example operationalinformation that can be stored in memory 986 can comprise, but is notlimited to, subscriber information; contracted services; maintenance andservice records; femto cell configuration (e.g., devices served throughfemto RAN 990; access control lists, or white lists); service policiesand specifications; privacy policies; add-on features; and so forth.

It is noted that femto network platform 980 and macro network platform910 can be functionally connected through one or more reference link(s)or reference interface(s). In addition, femto network platform 980 canbe functionally coupled directly (not illustrated) to one or more ofexternal network(s) 940, 950, 960, 965 or 967. Reference link(s) orinterface(s) can functionally link at least one of gateway node(s) 984or server(s) 986 to the one or more external networks 940, 950, 960, 965or 967.

FIG. 10 illustrates a wireless environment that comprises macro cellsand femtocells for wireless coverage in accordance with aspectsdescribed herein. In wireless environment 1005, two areas represent“macro” cell coverage; each macro cell is served by a base station 1010.It can be appreciated that macro cell coverage area 1005 and basestation 1010 can comprise functionality, as more fully described herein,for example, with regard to system 1000. Macro coverage is generallyintended to serve mobile wireless devices, like UE 1020 _(A), 1020 _(B),in outdoors locations. An over-the-air (OTA) wireless link 1035 providessuch coverage, the wireless link 1035 comprises a downlink (DL) and anuplink (UL), and utilizes a predetermined band, licensed or unlicensed,of the radio frequency (RF) spectrum. As an example, UE 1020 _(A), 1020_(B) can be a 3GPP Universal Mobile Telecommunication System (UMTS)mobile phone. It is noted that a set of base stations, its associatedelectronics, circuitry or components, base stations controlcomponent(s), and wireless links operated in accordance to respectivebase stations in the set of base stations form a radio access network(RAN). In addition, base station 1010 communicates via backhaul link(s)1051 with a macro network platform 1060, which in cellular wirelesstechnologies (e.g., 3rd Generation Partnership Project (3GPP) UniversalMobile Telecommunication System (UMTS), Global System for MobileCommunication (GSM)) represents a core network.

In an aspect, macro network platform 1060 controls a set of basestations 1010 that serve either respective cells or a number of sectorswithin such cells. Base station 1010 comprises radio equipment 1014 foroperation in one or more radio technologies, and a set of antennas 1012(e.g., smart antennas, microwave antennas, satellite dish(es) . . . )that can serve one or more sectors within a macro cell 1005. It is notedthat a set of radio network control node(s), which can be a part ofmacro network platform 1060; a set of base stations (e.g., Node B 1010)that serve a set of macro cells 1005; electronics, circuitry orcomponents associated with the base stations in the set of basestations; a set of respective OTA wireless links (e.g., links 1015 or1016) operated in accordance to a radio technology through the basestations; and backhaul link(s) 1055 and 1051 form a macro radio accessnetwork (RAN). Macro network platform 1060 also communicates with otherbase stations (not shown) that serve other cells (not shown). Backhaullink(s) 1051 or 1053 can comprise a wired backbone link (e.g., opticalfiber backbone, twisted-pair line, T1/E1 phone line, a digitalsubscriber line (DSL) either synchronous or asynchronous, an asymmetricADSL, or a coaxial cable . . . ) or a wireless (e.g., line-of-sight(LOS) or non-LOS) backbone link. Backhaul pipe(s) 1055 link disparatebase stations 1010. According to an aspect, backhaul link 1053 canconnect multiple femto access points 1030 and/or controller components(CC) 1001 to the femto network platform 1002. In one example, multiplefemto APs can be connected to a routing platform (RP) 1087, which inturn can be connect to a controller component (CC) 1001. Typically, theinformation from UEs 1020 _(A) can be routed by the RP 1087, forexample, internally, to another UE 1020 _(A) connected to a disparatefemto AP connected to the RP 1087, or, externally, to the femto networkplatform 1002 via the CC 1001, as discussed in detail supra.

In wireless environment 1005, within one or more macro cell(s) 1005, aset of femtocells 1045 served by respective femto access points (APs)1030 can be deployed. It can be appreciated that, aspects of the subjectinnovation can be geared to femtocell deployments with substantive femtoAP density, e.g., 10⁴-10⁷ femto APs 1030 per base station 1010.According to an aspect, a set of femto access points 1030 ₁-1030 _(N),with N a natural number, can be functionally connected to a routingplatform 1087, which can be functionally coupled to a controllercomponent 1001. The controller component 1001 can be operationallylinked to the femto network platform 1002 by employing backhaul link(s)1053. Accordingly, UE 1020 _(A) connected to femto APs 1030 ₁-1030 _(N)can communicate internally within the femto enterprise via the routingplatform (RP) 1087 and/or can also communicate with the femto networkplatform 1002 via the RP 1087, controller component 1001 and thebackhaul link(s) 1053. It can be appreciated that although only onefemto enterprise is depicted in FIG. 10, multiple femto enterprisenetworks can be deployed within a macro cell 1005.

It is noted that while various aspects, features, or advantagesdescribed herein have been illustrated through femto access point(s) andassociated femto coverage, such aspects and features also can beexploited for home access point(s) (HAPs) that provide wireless coveragethrough substantially any, or any, disparate telecommunicationtechnologies, such as for example Wi-Fi (wireless fidelity) or picocelltelecommunication. Additionally, aspects, features, or advantages of thesubject innovation can be exploited in substantially any wirelesstelecommunication, or radio, technology; for example, Wi-Fi, WorldwideInteroperability for Microwave Access (WiMAX), Enhanced General PacketRadio Service (Enhanced GPRS), 3GPP LTE, 3GPP2 UMB, 3GPP UMTS, HSPA,HSDPA, HSUPA, or LTE Advanced. Moreover, substantially all aspects ofthe subject innovation can comprise legacy telecommunicationtechnologies.

With respect to FIG. 10, in example embodiment 1000, base station AP1010 can receive and transmit signal(s) (e.g., traffic and controlsignals) from and to wireless devices, access terminals, wireless portsand routers, etc., through a set of antennas 1012 ₁-1012 _(N). It shouldbe appreciated that while antennas 1012 ₁-1012 _(N) are a part ofcommunication platform 1025, which comprises electronic components andassociated circuitry that provides for processing and manipulating ofreceived signal(s) (e.g., a packet flow) and signal(s) (e.g., abroadcast control channel) to be transmitted. In an aspect,communication platform 1025 comprises a transmitter/receiver (e.g., atransceiver) 1066 that can convert signal(s) from analog format todigital format upon reception, and from digital format to analog formatupon transmission. In addition, receiver/transmitter 1066 can divide asingle data stream into multiple, parallel data streams, or perform thereciprocal operation. Coupled to transceiver 1066 is amultiplexer/demultiplexer 1067 that facilitates manipulation of signalin time and frequency space. Electronic component 1067 can multiplexinformation (data/traffic and control/signaling) according to variousmultiplexing schemes such as time division multiplexing (TDM), frequencydivision multiplexing (FDM), orthogonal frequency division multiplexing(OFDM), code division multiplexing (CDM), space division multiplexing(SDM). In addition, mux/demux component 1067 can scramble and spreadinformation (e.g., codes) according to substantially any code known inthe art; e.g., Hadamard-Walsh codes, Baker codes, Kasami codes,polyphase codes, and so on. A modulator/demodulator 1068 is also a partof operational group 1025, and can modulate information according tomultiple modulation techniques, such as frequency modulation, amplitudemodulation (e.g., M-ary quadrature amplitude modulation (QAM), with M apositive integer), phase-shift keying (PSK), and the like.

Referring now to FIG. 11, there is illustrated a block diagram of anexemplary computer system operable to execute the disclosedarchitecture. In order to provide additional context for various aspectsof the disclosed subject matter, FIG. 11 and the following discussionare intended to provide a brief, general description of a suitablecomputing environment 1100 in which the various aspects of the disclosedsubject matter can be implemented. Additionally, while the disclosedsubject matter described above may be suitable for application in thegeneral context of computer-executable instructions that may run on oneor more computers, those skilled in the art will recognize that thedisclosed subject matter also can be implemented in combination withother program modules and/or as a combination of hardware and software.

Generally, program modules comprise routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the disclosed subject matter may also bepracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

A computer typically comprises a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and comprises both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can comprise eithervolatile or nonvolatile, removable and non-removable media implementedin any method or technology for storage of information such ascomputer-readable instructions, data structures, program modules orother data. Computer storage media comprises, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM,digital versatile disk (DVD) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, andcomprises any information delivery media. The term “modulated datasignal” means a signal that has one or more of its characteristics setor changed in such a manner as to encode information in the signal. Byway of example, and not limitation, communication media comprises wiredmedia such as a wired network or direct-wired connection, and wirelessmedia such as acoustic, RF, infrared and other wireless media.Combinations of the any of the above should also be included within thescope of computer-readable media.

Still referring to FIG. 11, the exemplary environment 1100 forimplementing various aspects of the disclosed subject matter comprises acomputer 1102, the computer 1102 including a processing unit 1104, asystem memory 1106 and a system bus 1108. The system bus 1108 couples tosystem components including, but not limited to, the system memory 1106to the processing unit 1104. The processing unit 1104 can be any ofvarious commercially available processors. Dual microprocessors andother multi-processor architectures may also be employed as theprocessing unit 1104.

The system bus 1108 can be any of several types of bus structure thatmay further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1106comprises read-only memory (ROM) 1110 and random access memory (RAM)1112. A basic input/output system (BIOS) is stored in a non-volatilememory 1110 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1102, such as during start-up. The RAM 1112 can also comprise ahigh-speed RAM such as static RAM for caching data.

The computer 1102 further comprises an internal hard disk drive (HDD)1114 (e.g., EIDE, SATA), which internal hard disk drive 1114 may also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1116, (e.g., to read from or write to aremovable diskette 1118) and an optical disk drive 1120, (e.g., readinga CD-ROM disk 1122 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1114, magnetic diskdrive 1116 and optical disk drive 1120 can be connected to the systembus 1108 by a hard disk drive interface 1124, a magnetic disk driveinterface 1126 and an optical drive interface 1128, respectively. Theinterface 1124 for external drive implementations comprises at least oneor both of Universal Serial Bus (USB) and IEEE1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject matter disclosed herein.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1102, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, may also be used in the exemplary operating environment, andfurther, that any such media may contain computer-executableinstructions for performing the methods of the disclosed subject matter.

A number of program modules can be stored in the drives and RAM 1112,including an operating system 1130, one or more application programs1132, other program modules 1134 and program data 1136. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1112. It is appreciated that the disclosed subjectmatter can be implemented with various commercially available operatingsystems or combinations of operating systems.

A user can enter commands and information into the computer 1102 throughone or more wired/wireless input devices, e.g., a keyboard 1138 and apointing device, such as a mouse 1140. Other input devices (not shown)may comprise a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1104 through an input deviceinterface 1142 that is coupled to the system bus 1108, but can beconnected by other interfaces, such as a parallel port, an IEEE1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1144 or other type of display device is also connected to thesystem bus 1108 via an interface, such as a video adapter 1146. Inaddition to the monitor 1144, a computer typically comprises otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1102 may operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1148. The remotecomputer(s) 1148 can be a workstation, a server computer, a router, apersonal computer, a mobile device, portable computer,microprocessor-based entertainment appliance, a peer device or othercommon network node, and typically comprises many or all of the elementsdescribed relative to the computer 1102, although, for purposes ofbrevity, only a memory/storage device 1150 is illustrated. The logicalconnections depicted comprise wired/wireless connectivity to a localarea network (LAN) 1152 and/or larger networks, e.g., a wide areanetwork (WAN) 1154. Such LAN and WAN networking environments arecommonplace in offices and companies, and facilitate enterprise-widecomputer networks, such as intranets, all of which may connect to aglobal communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 1102 isconnected to the local network 1152 through a wired and/or wirelesscommunication network interface or adapter 1156. The adapter 1156 mayfacilitate wired or wireless communication to the LAN 1152, which mayalso comprise a wireless access point disposed thereon for communicatingwith the wireless adapter 1156.

When used in a WAN networking environment, the computer 1102 cancomprise a modem 1158, or is connected to a communications server on theWAN 1154, or has other means for establishing communications over theWAN 1154, such as by way of the Internet. The modem 1158, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1108 via the serial port interface 1142. In a networkedenvironment, program modules depicted relative to the computer 1102, orportions thereof, can be stored in the remote memory/storage device1150. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer 1102 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This comprises at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE802.11 (a, b,g, n, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE802.3 or Ethernet). Wi-Finetworks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 11Mbps (802.11b) or 54 Mbps (802.11a) data rate, for example, or withproducts that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic “10BaseT” wiredEthernet networks used in many offices.

What has been described above comprises examples of the variousembodiments. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the embodiments, but one of ordinary skill in the art mayrecognize that many further combinations and permutations are possible.Accordingly, the detailed description is intended to embrace all suchalterations, modifications, and variations that fall within the spiritand scope of the appended claims.

As used in this application, the terms “system,” “component,”“interface,” and the like are generally intended to refer to acomputer-related entity or an entity related to an operational machinewith one or more specific functionalities. The entities disclosed hereincan be either hardware, a combination of hardware and software,software, or software in execution. For example, a component may be, butis not limited to being, a process running on a processor, a processor,an object, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components mayreside within a process and/or thread of execution and a component maybe localized on one computer and/or distributed between two or morecomputers. These components also can execute from various computerreadable storage media having various data structures stored thereon.The components may communicate via local and/or remote processes such asin accordance with a signal having one or more data packets (e.g., datafrom one component interacting with another component in a local system,distributed system, and/or across a network such as the Internet withother systems via the signal). As another example, a component can be anapparatus with specific functionality provided by mechanical partsoperated by electric or electronic circuitry that is operated bysoftware or firmware application(s) executed by a processor, wherein theprocessor can be internal or external to the apparatus and executes atleast a part of the software or firmware application. As yet anotherexample, a component can be an apparatus that provides specificfunctionality through electronic components without mechanical parts,the electronic components can comprise a processor therein to executesoftware or firmware that confers at least in part the functionality ofthe electronic components. An interface can comprise input/output (I/O)components as well as associated processor, application, and/or APIcomponents.

Furthermore, the disclosed subject matter may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from by acomputing device.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor also can be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” “queue”, and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can comprise both volatile andnonvolatile memory. In addition, memory components or memory elementscan be removable or stationary. Moreover, memory can be internal orexternal to a device or component, or removable or stationary. Memorycan comprise various types of media that are readable by a computer,such as hard-disc drives, zip drives, magnetic cassettes, flash memorycards or other types of memory cards, cartridges, or the like.

By way of illustration, and not limitation, nonvolatile memory cancomprise read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can comprise random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated exemplary aspects of the embodiments. In thisregard, it will also be recognized that the embodiments comprises asystem as well as a computer-readable medium having computer-executableinstructions for performing the acts and/or events of the variousmethods.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disk (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or other tangible and/ornon-transitory media which can be used to store desired information.Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

On the other hand, communications media typically embodycomputer-readable instructions, data structures, program modules orother structured or unstructured data in a data signal such as amodulated data signal, e.g., a carrier wave or other transportmechanism, and comprises any information delivery or transport media.The term “modulated data signal” or signals refers to a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in one or more signals. By way of example, and notlimitation, communications media comprise wired media, such as a wirednetwork or direct-wired connection, and wireless media such as acoustic,RF, infrared and other wireless media

Further, terms like “user equipment,” “user device,” “mobile device,”“mobile,” station,” “access terminal,” “terminal,” “handset,” andsimilar terminology, generally refer to a wireless device utilized by asubscriber or user of a wireless communication network or service toreceive or convey data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably in the subject specification and relateddrawings. Likewise, the terms “access point,” “node B,” “base station,”“evolved Node B,” “cell,” “cell site,” and the like, can be utilizedinterchangeably in the subject application, and refer to a wirelessnetwork component or appliance that serves and receives data, control,voice, video, sound, gaming, or substantially any data-stream orsignaling-stream from a set of subscriber stations. Data and signalingstreams can be packetized or frame-based flows. It is noted that in thesubject specification and drawings, context or explicit distinctionprovides differentiation with respect to access points or base stationsthat serve and receive data from a mobile device in an outdoorenvironment, and access points or base stations that operate in aconfined, primarily indoor environment overlaid in an outdoor coveragearea. Data and signaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” andthe like are employed interchangeably throughout the subjectspecification, unless context warrants particular distinction(s) amongthe terms. It should be appreciated that such terms can refer to humanentities, associated devices, or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth. In addition, the terms “wirelessnetwork” and “network” are used interchangeable in the subjectapplication, when context wherein the term is utilized warrantsdistinction for clarity purposes such distinction is made explicit.

Moreover, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

In addition, while a particular feature may have been disclosed withrespect to only one of several implementations, such feature may becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.Furthermore, to the extent that the terms “includes” and “including” andvariants thereof are used in either the detailed description or theclaims, these terms are intended to be inclusive in a manner similar tothe term “comprising.”

What is claimed is:
 1. An access point device, comprising: a processor;and a memory that stores executable instructions that, when executed bythe processor, facilitate performance of operations, comprising:determining that a subscriber device, which has attached to the accesspoint device to communicate machine data, is a machine-to-machinedevice; in response to a determination that the machine data has beencommunicated, detaching the machine-to-machine device independently ofan inactivity timer that effectuates the detaching when the inactivitytimer has reached a threshold time; and purging state informationrelating to the machine-to-machine device independently of theinactivity timer.
 2. The access point device of claim 1, wherein theoperations further comprise transmitting, to a network device, purgedata representative of an instruction to purge state data relating tothe machine-to-machine device independently of the inactivity timer. 3.The access point device of claim 2, wherein the network device isselected from a group comprising: a serving gateway device, a packetdata network gateway device, and a mobility management entity device;and wherein the state data is selected from a group comprising: an IPanchor state of the machine-to-machine device, a mobility anchor stateof the machine-to-machine device, a mobility state of themachine-to-machine device, a handover state of the machine-to-machinedevice, and a tracking area of the machine-to-machine device.
 4. Theaccess point device of claim 1, wherein the detaching themachine-to-machine device is further based on a security protocol. 5.The access point device of claim 3, wherein the operations furthercomprise ignoring, based on the security protocol, a request from themachine-to-machine device to attach to the access point device.
 6. Theaccess point device of claim 5, wherein the security protocol indicatesthe request is to be ignored in response to a determination that therequest has not been made with respect to a defined schedule.
 7. Theaccess point device of claim 5, wherein the security protocol indicatesthe request is to be ignored in response to a determination that themachine data is greater in size than a defined threshold size.
 8. Theaccess point device of claim 1, wherein the operations further comprise:in response to the determination that the subscriber device is themachine-to-machine device, excluding the machine-to-machine device fromparticipation in a network signaling procedure.
 9. The access pointdevice of claim 8, wherein the network signaling procedure relates tomeasurement and reporting associated with a load-balancing procedure.10. The access point device of claim 1, wherein the determination thatthe subscriber device is the machine-to-machine device is based on dataselected from a group comprising: first data representative of a levelof service provisioned for the subscriber device, second datarepresentative of an Internet protocol address associated with thesubscriber device, third data representative of a media access controladdress associated with the subscriber device, fourth datarepresentative of a device category as defined by a third generationpartnership project specification, and fifth data representative of amachine-to-machine indicator received from the subscriber device thatindicates the subscriber device is the machine-to-machine device.
 11. Amethod, comprising: determining, by a system comprising a processor,that a subscriber device, which attaches to an access point device tocommunicate machine data, is a machine-to-machine device; determining,by the system, that the machine data has been communicated; determining,by the system, that the machine-to-machine device has been detached fromthe access point device independently of an inactivity timer that causesa detaching upon expiration of an inactivity timer; and purging, by thesystem, state information relating to the machine-to-machine deviceindependently of the inactivity timer.
 12. The method of claim 11,further comprising transmitting, by the system, purge data to a networkdevice, wherein the purge data is representative of an instruction topurge state data relating to the machine-to-machine device independentlyof the inactivity timer.
 13. The method of claim 11, further comprisingactivating, by the system, a security procedure in response to arequest, by the machine-to-machine device, to attach to the access pointdevice.
 14. The method of claim 13, wherein the security protocolindicates the request to attach to the access point device is to beignored in response to a determination that the request is not accordingto a defined schedule.
 15. The method of claim 13, wherein the securityprotocol indicates the request to attach to the access point device isto be ignored in response to a determination that the machine data islarger than a defined size threshold.
 16. The method of claim 11,further comprising, in response to the determination that the subscriberdevice is the machine-to-machine device, excluding, by the system, themachine-to-machine device from participation in a network signalingprocedure.
 17. A machine-readable storage medium, comprising executableinstructions that, when executed by a processor, facilitate performanceof operations, comprising: determining that a subscriber device that hasattached to an access point device to communicate machine data is amachine-to-machine device; determining that the machine data has beencommunicated; determining that the machine-to-machine device has beendetached from the access point device independently of an inactivitytimer that triggers a detaching procedure upon expiration of aninactivity timer; and purging state information relating to themachine-to-machine device independently of the inactivity timer.
 18. Themachine-readable storage medium of claim 17, wherein the operationsfurther comprise communicating purge data to a network device, andwherein the purge data is representative of an instruction to purge,independently of the inactivity timer, state data relating to themachine-to-machine device.
 19. The machine-readable storage medium ofclaim 17, wherein the operations further comprise activating a securityprocedure in response to a request, by the machine-to-machine device, toattach to the access point device.
 20. The machine-readable storagemedium of claim 19, wherein the security protocol indicates the requestto attach to the access point device is to be ignored in response to adetermination that the request is received at a time not specified by adefined schedule.